2015-01-07 - 16422 - Service Request - Not able to cancel GR document #MMPPSupport
2014-01-07 - 16422.100 - Breakfix - Not able to cancel GR document
Problem Summary
Not able to cancel GR document
Admin Info
| Purpose |
Not able to cancel GR document |
| Requested By |
Babu Lankipalli |
| Spec Created By |
Laxman, Adithya |
| Spec Created Date |
01/09/2015 |
| Spec QA by |
Adithya |
| Objects |
N/A |
| Document Status |
Complete |
Detailed Problem Description
Could not able to cancel GR document/post short quantities.
Below is the error Message when a GR Document is being cancelled:
Solution Analysis and Recommendations
[Discuss this section with Requester and get approval prior to beginning work]
After Analysis understand that these Purchase Orders are the SNC NB POs for which we are creating an Inbound Delivery (Not Further Used) for only doing a MIGO.
When a Confirmation Key in the Purchase Order is ZSNC, the system doesn't allow MIGO until ZT Confirmation Cat key is updated, this is because in configuration MRP Relevant, GR Relevant and GR Assignment Check boxes are flagged for ZT Confirmation category, which means that to do GR it is mandatory for ZT Confirmation to be updated in the PO confirmations
When MIGO is done manually for the POs, Quantity Reduction Field is updated DABMG but when the MIGO is done using an IDOC this field is not updated which is causing the issue.
We have found Few OSS Notes Related to this Issue:
Sent a request to Implement the below OSS Notes:
1. 1561928 Implemented Did not solve the Issue.
0001561928_OSSNOTE_GR.pdf
2. 1919406 Implemented Did not solve the Issue.
0001919406.pdf
3. 1983313 Implemented Did not solve the Issue.
0001983313.pdf
SAP is Working on the Issue in Parallel.
Discussion With SAP:
It has recommended a KBA 2044484 (KBA) the corresponding Notes in this KBA Needs to be Implemented.
BMS Reply:
Submitted a Detailed Document to SAP:
GR_Cancellation.docx
SAP Reply on 02/09/2015:
I checked the include LEINBF0W in system NED/300 and please find the details below. You need to now implement 3 notes in the following sequence.
1. Implement the note 1836751.
2. Implement AFS note 1919406.
3. Implement the AFS note 1983313.
Kindly get back to us in case of further issues/clarifications from our end.
Reply From BMS on 02/09/2015:
We have already implemented OSS Notes 1919406 & 1983313 but We can try Implementing it in Sequence with the additional Notes Provided by SAP
Reply From NE on 02/14/2015:
The Notes are Implemented please test and provide the results:
Reply From BMS on 02/16/2015:
Tested to cancel the material document for Purchase Order 4600007570 but still same error is thrown. The Implementation of the Notes in sequence did not work.
SAP Reply on 02/23/2015:
The issue occurred since the field MSEG-ETENS is not filled before calling MB_CREATE_GOODS_MOVEMENT. Please refer to note 520813 (question 17) for clarification.
Background: At present, you cannot assign the sequence number for the purchase order confirmation (EKES-ETENS) to the IDOC at item level in the interface.
==> this is the same for customers who are using the message type WMMBXY (L_IDOC_INPUT_WMMBXY).
As we can't determine the confirmation the customer has to fill this in the idoc input function on his own. This means:==> for customers who are using WMMBXY: they have to user customer function 'EXIT_SAPLLMDE_002' to specify and fill field MSEG-ETENS before MB_CREATE_GOODS_MOVEMENT is called.
I'm sorry that I can't give you a standard solution because we can't determine in this case the confirmation. IDOC postings are always technical interfaces where the customer has to provide the input data. We do not support every postings like we do that in our online transactions. But I believe that within the given proposal (fill MSEG-ETENS) your problem will be solved.
The note 906314 describes how the extension structure can be used to pass on the ETENS value instead of directly using the User Exit.
It gives details of how to enhance the structure. You can follow the steps to populate the ETENS value. Kindly get back to us in case of further issues/clarifications from our end or else please confirm the message at your convenience.
Kindly get back to us in case of further issues/clarifications from our end or else please confirm the message at your convenience.
BMS Reply on 02/26/2015
As per the reply from SAP, enhanced the function module L_IDOC_INPUT_WMMBXY.
- Fetched the sequence number from EKES table based on the PO, Item and Grid
- Passed the sequence number (EKES-ETENS) to MSEG-ETENS
A Document is sent to SAP on 03/03/2015
GR Cancellation Issue-IDOC_03032015.doc
SAP Reply on 03/16/2015
We would like inform you that all the MB transactions have now been replaced with transaction MIGO. Please refer SAP note "1804812" for more details about the same. We therefore request you to use MIGO transaction instead of MBST to avoid errors.
BMS Reply on 03/17/2015
When we have tried to reverse the GR document using MIGO we have got dump in DEV 300, There is a FM "MB_CREATE_MATERIAL_DOCUMENT_UT" which is raising exception.
GR Cancel.docx
SAP Reply on 04/17/2015
Please provide the IDOC which is un processed.
BMS Reply on 04/20/2015
PO # 4600007885 for which we can try doing MIGO with IDOC 359821.
Test Plan
[List test scenarios/cases to be executed here]| Test ID |
Test Scenario |
Expected Results |
| MM001 |
Create purchase order using SNC vendor. Then create the inbound delivery and do the goods receipt using IDOC. |
GR document should cancel/ reverse with out any error |
Resolution
[Provide complete technical details for configuration or programming here]
As a Work Around Inventory is adjusted with the Material movements/Physical Inventory where ever is required to match the inventory.
The issue is resolved by a OSS note given by SAP
Issues
[List Issues / Bugs identified in configuration or development]